Method, Apparatus, and Program to Efficiently Calculate Cache Prefetching Patterns for Loops

ABSTRACT

A mechanism is provided that identifies instructions that access storage and may be candidates for catch prefetching. The mechanism augments these instructions so that any given instance of the instruction operates in one of four modes, namely normal, unexecuted, data gathering, and validation. In the normal mode, the instruction merely performs the function specified in the software runtime environment. An instruction in unexecuted mode, upon the next execution, is placed in data gathering mode. When an instruction in the data gathering mode is encountered, the mechanism of the present invention collects data to discover potential fixed storage access patterns. When an instruction is in validation mode, the mechanism of the present invention validates the presumed fixed storage access patterns.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates to data processing and, in particular, tocache prefetching in data processing systems. Still more particularly,the present invention provides a method, apparatus, and program toefficiently calculate cache prefetching patterns for loops.

2. Description of Related Art

Many current software runtime environments use cache prefetching.Prefetching works as follows: upon detecting a sequential memory accesspattern in an executing program the software environment starts toprefetch cache lines from main memory to L1/L2 caches. The purpose is tomake the data available to the executing program in the low latencycache when the data is actually accessed later, thereby reducing theaverage memory access time.

An example of a software runtime environment is a Java™ virtual machine(JVM). There are loops in the Java™ programming language, for example,that iterate over a data structure in such a way that access to storagefollows a predictable pattern. If a JVM had knowledge of such a pattern,it could insert cache prefetch instructions into the code stream ordetermine unroll factors that would speed up execution of the loop.

Thus, while interpreting or just-in-time (JIT) compiling bytecode, theJVM may look for access patterns that are regular. The JVM may thenleave a record of such patterns, such as expected stride, forexploitation by a JIT compiler and may possibly insert prefetchinstructions or determine loop unrolling factors.

Stride is a distance between successive memory accesses. Current methodsfor determining stride using well-known static compiler techniques toevaluate variables are used to index a loop. To augment this analysis,the JVM compiler may profile a given routine and collect data. Thisrequires either building a bytecode interpreter before generating binarycode, generating bytecode to perform the profiling, or generating abinary version with profiling hooks and then later recompiling theroutine utilizing the profiling information. All of these approaches paya high processing overhead. Additionally, if data structures other thanthe profile information are being manipulated, such as B-trees forexample, then analysis becomes even more difficult.

SUMMARY OF THE INVENTION

The present invention recognizes the disadvantages of the prior art andprovides a mechanism that identifies instructions that access storageand may be candidates for cache prefetching. The mechanism augmentsthese instructions so that any given instance of the instructionoperates in one of four modes, namely normal, unexecuted, datagathering, and validation. In the normal mode, the instruction merelyperforms the function specified in the software runtime environment. Aninstruction in unexecuted mode, upon the next execution, is placed indata gathering mode. When an instruction in the data gathering mode isencountered, the mechanism of the present invention collects data todiscover potential fixed storage access patterns. When an instruction isin validation mode, the mechanism of the present invention validates thepresumed fixed storage access patterns.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 is a pictorial representation of a data processing system inwhich the present invention may be implemented in accordance with apreferred embodiment of the present invention;

FIG. 2 is a block diagram of a data processing system in which thepresent invention may be implemented;

FIG. 3 is a block diagram illustrating a software runtime environment inaccordance with a preferred embodiment of the present invention;

FIGS. 4A & 4B illustrate an example data gathering structure for a loadinstruction in accordance with a preferred embodiment of the presentinvention; and

FIGS. 5A-5E are flowcharts illustrating operation of a virtual machinefor determining cache prefetching patterns for loops in accordance witha preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention provides a method, apparatus and computer programproduct for efficiently calculating cache prefetching patterns forloops. The data processing device may be a single-processor computingdevice, a multiprocessing data processing system, or a virtual processorenvironment in which multiple processors and multiple layers of softwaremay be utilized to perform various aspects of the present invention.Therefore, the following FIGS. 1 and 2 are provided as exemplarydiagrams of data processing environments in which the present inventionmay be implemented. It should be appreciated that FIGS. 1 and 2 are onlyexemplary and are not intended to assert or imply any limitation withregard to the environments in which the present invention may beimplemented. Many modifications to the depicted environments may be madewithout departing from the spirit and scope of the present invention.

With reference now to the figures and in particular with reference toFIG. 1, a pictorial representation of a data processing system in whichthe present invention may be implemented is depicted in accordance witha preferred embodiment of the present invention. A computer 100 isdepicted which includes system unit 102, video display terminal 104,keyboard 106, storage devices 108, which may include floppy drives andother types of permanent and removable storage media, and mouse 110.Additional input devices may be included with personal computer 100,such as, for example, a joystick, touchpad, touch screen, trackball,microphone, and the like.

Computer 100 can be implemented using any suitable computer, such as anIBM eServer™ computer or IntelliStation® computer, which are products ofInternational Business Machines Corporation, located in Armonk, N.Y.Although the depicted representation shows a computer, other embodimentsof the present invention may be implemented in other types of dataprocessing systems, such as a network computer. Computer 100 alsopreferably includes a graphical user interface (GUI) that may beimplemented by means of systems software residing in computer readablemedia in operation within computer 100.

With reference now to FIG. 2, a block diagram of a data processingsystem is shown in which the present invention may be implemented. Dataprocessing system 200 is an example of a computer, such as computer 100in FIG. 1, in which code or instructions implementing the processes ofthe present invention may be located. In the depicted example, dataprocessing system 200 employs a hub architecture including a northbridge and memory controller hub (MCH) 208 and a south bridge andinput/output (I/O) controller hub (ICH) 210. Processor 202, main memory204, and graphics processor 218 are connected to MCH 208. Graphicsprocessor 218 may be connected to the MCH through an acceleratedgraphics port (AGP), for example.

In the depicted example, local area network (LAN) adapter 212, audioadapter 216, keyboard and mouse adapter 220, modem 222, read only memory(ROM) 224, hard disk drive (HDD) 226, CD-ROM driver 230, universalserial bus (USB) ports and other communications ports 232, and PCI/PCIedevices 234 may be connected to ICH 210. PCI/PCIe devices may include,for example, Ethernet adapters, add-in cards, PC cards for notebookcomputers, etc. PCI uses a cardbus controller, while PCIe does not. ROM224 may be, for example, a flash binary input/output system (BIOS). Harddisk drive 226 and CD-ROM drive 230 may use, for example, an integrateddrive electronics (IDE) or serial advanced technology attachment (SATA)interface. A super I/O (SIO) device 236 may be connected to ICH 210.

An operating system runs on processor 202 and is used to coordinate andprovide control of various components within data processing system 200in FIG. 2. The operating system may be a commercially availableoperating system such as Windows XP™, which is available from MicrosoftCorporation. An object oriented programming system, such as Java™programming system, may run in conjunction with the operating system andprovides calls to the operating system from Java™ programs orapplications executing on data processing system 200. “JAVA” is atrademark of Sun Microsystems, Inc. Instructions for the operatingsystem, the object-oriented programming system, and applications orprograms are located on storage devices, such as hard disk drive 226,and may be loaded into main memory 204 for execution by processor 202.The processes of the present invention are performed by processor 202using computer implemented instructions, which may be located in amemory such as, for example, main memory 204, memory 224, or in one ormore peripheral devices 226 and 230.

Processor 202 includes a cache 203, which may be, for example, an L1 orL2 cache. Many current software runtime environments use data cacheprefetching where, upon detecting sequential memory access pattern in anexecuting program, the software environment starts to prefetch cachelines from main memory 204 to caches 203. The purpose is to make thedata available to the executing program in the low latency cache whenthe data is actually accessed later, thereby reducing the average memoryaccess time.

The present invention provides a mechanism that identifies instructionsthat access storage and may be candidates for cache prefetching. Themechanism of the present invention provides a much cheaper (faster) andpossibly more accurate method to obtain stride patterns for use by ajust-in-time (JIT) compiler when generating binary code. Because themechanism records the relationship of actual memory access patternsregardless of data structure, the mechanism of the present invention maybe beneficial to any type of data structure. The mechanism of thepresent invention focuses on hardware architectures containingprocessor-specific data caches, although multiprocessors sharing cachescan possibly benefit as well.

Those of ordinary skill in the art will appreciate that the hardware inFIG. 2 may vary depending on the implementation. Other internal hardwareor peripheral devices, such as flash memory, equivalent non-volatilememory, or optical disk drives and the like, may be used in addition toor in place of the hardware depicted in FIG. 2. Also, the processes ofthe present invention may be applied to a multiprocessor data processingsystem.

For example, data processing system 200 may be a personal digitalassistant (PDA), which is configured with flash memory to providenon-volatile memory for storing operating system files and/oruser-generated data. The depicted example in FIG. 2 and above-describedexamples are not meant to imply architectural limitations. For example,data processing system 200 also may be a tablet computer, laptopcomputer, or telephone device in addition to taking the form of a PDA.

FIG. 3 is a block diagram illustrating a software runtime environment inaccordance with a preferred embodiment of the present invention. Virtualmachine 310 receives an instruction stream from a program to beexecuted. Virtual machine 310 may be, for example, a Java™ virtualmachine and the instruction stream may represent one or more methodsexecuting as part of one or more classes, which execute in one or morethreads. In an exemplary embodiment of the present invention, virtualmachine 310 includes a JIT compiler. However, the present invention isnot intended to be limited to the Java™ programming system.

Instructions within the instruction stream may include load instructionsthat access memory 324. In the Java™ programming language, loadinstructions may include, for example, getfield instructions, aaloadfield instructions, and getstatic instructions to load values fromfields of objects, arrays, and global objects. Upon detecting asequential memory access pattern, virtual machine 310 may start toprefetch cache lines from main memory 324 to caches 322. The purpose isto make the data available to the executing program in the low latencycache when the data is actually accessed later, thereby reducing theaverage memory access time.

Virtual machine 310 augments load instructions such that any instance ofa load instruction operates in one of four modes, namely “normal,”“unexecuted,” “data gathering,” and “validation.” In the normal mode,the instruction merely performs the function specified in the softwareruntime environment. An instruction in unexecuted mode, upon the nextexecution, is placed in data gathering mode. When an instruction in thedata gathering mode is encountered, virtual machine 310 collects accesspattern data 312 to discover potential fixed storage access patterns.When an instruction is in validation mode, virtual machine 310 validatesthe presumed fixed storage access patterns. In one exemplary embodimentof the present invention, virtual machine 310 distinguishes betweenmodes by using a separate op-code for each type of load instructionoperating in anything but the normal mode. For example, virtual machine310 may provide a getfield_gather instruction in addition to thepreviously existing getfield instruction.

Certain data is associated with a load instruction in the data gatheringmode. The data gathering structure may include, for example, a threadidentifier, an indication of the last address referenced, an array ofsome number of differences between addresses of the successive accesses(differences array), and a count of the number of such data gathered maybe recorded in a data gathering structure. During data gathering,virtual machine 310 may collect a predetermined number of samples, suchas 11 for example. In one exemplary embodiment, virtual machine 310 mayassociate a given load instruction with a particular set of data byre-using the field reference of the original instruction to indicate thelocation of the associated data. Also, virtual machine 310 may allocatea fixed array of records and assume that at any given time a smallnumber of actual load instructions are operating in data gathering mode.

FIG. 4A illustrates an example data gathering structure for a loadinstruction in accordance with a preferred embodiment of the presentinvention. In the example shown in FIG. 4A, the load instruction is agetfield instruction, although similar data gathering structures mayalso be defined for other known load instructions within a softwareprogramming language.

Certain data is associated with a load instruction operating in thevalidation mode. The validation structure may include, for example, thepresumed value of the difference in addresses in successive executionsof the instruction, an indication of the last address referenced by theinstruction for each thread, a count of the number of times a successiveaccess was within a single cache line of the predicted value, and acount of the number of times a successive access was not within a singlecache line of the predicted value. The expectation is that loadinstructions will rarely operate in validation mode. Therefore, it islikely that a small number of validation structures will be allocated.

FIG. 4B illustrates an example data validation structure for a loadinstruction in accordance with a preferred embodiment of the presentinvention. In the example shown in FIG. 4B, the load instruction is agetfield instruction, although similar data validation structures mayalso be defined for other known load instructions within a softwareprogramming language.

FIGS. 5A-5E are flowcharts illustrating operation of a virtual machinefor determining cache prefetching patterns for loops in accordance witha preferred embodiment of the present invention. More particularly, withreference to FIG. 5A, operation begins and loads the method ofinstructions (block 501). The virtual machine then determines which loadinstructions are in loops (block 502). The load instructions in loopsmay be determined by identifying load instructions that appear between alabel and a backward branch to that label. These load instructions areinitialized to the unexecuted mode (block 503). In an exemplaryembodiment, instructions may be placed in a mode by replacing op-codesas discussed above.

A determination is made as to whether an exit condition exists (block504). An exit condition may exist, for example when the virtual machineshuts down. If an exit condition exists, operation ends. Otherwise, adetermination is made as to whether a load instruction in unexecutedmode is to be executed (block 505). If a load instruction in unexecutedmode is not encountered, a determination is made as to whether a loadinstruction in data gathering mode is to be executed (block 506). If aload instruction in data gathering mode is not encountered, adetermination is made as to whether a load instruction in validationmode is to be executed (block 507). If a load instruction in validationmode is not encountered, operation returns to block 504 to determinewhether an exit condition exists. Operation continues in this loop,executing normal instructions, including load instructions in normalmode, until an exit condition exists or a non-normal load instruction isencountered.

If a load instruction in unexecuted mode is encountered in block 505,operation proceeds to block 508 in FIG. 5B where a determination is madeas to whether resources are exhausted. If resources are exhausted, themechanism places the load instruction in normal mode (block 509),executes the instruction (block 510), and returns control to the virtualmachine (block 511). Thereafter, operation returns to block 504 in FIG.5A to determine whether an exit condition exists.

If resources are not exhausted in block 508, the virtual machineprovisions a data gathering structure for the load instruction (block512). The virtual machine then sets the thread identification (ID) tothe currently executing thread (block 513) and sets the difference countto zero (block 514). The possibility of two threads executing a loadinstruction in this mode is not high. Furthermore, the danger of twothreads executing these initializations simultaneously isinconsequential. It is assumed that writing this field is atomic (4-bytewrites are typically atomic).

Next, a determination is made as to whether the current ID and thethread ID saved in the data gathering structure are the same (block515). If the IDs are the same, then the effective address of the data tobe loaded is calculated (block 516) and stored in the last addressreferenced field of the data gathering structure (block 517). Then, thevirtual machine initializes the differences array and initializes thedifference count to zero (block 518). The virtual machine also placesthe load instruction in data gathering mode (block 519) and operationreturns to block 504 in FIG. 5A to determine whether an exit conditionexists.

If the thread ID is not the same as the thread ID stored in the datagathering structure in block 515, then there was a race condition withanother thread. In this case, the virtual machine lets the other threadset the last address referenced field (block 520) and operation returnsto block 504 in FIG. 5A to determine whether an exit condition exists.

If a load instruction in data gathering mode is encountered in block506, operation proceeds to block 521 in FIG. 5C where a determination ismade as to whether the thread terminates. If the thread associated withthe instruction terminates, the data gathering structure is recoveredfrom memory (block 522) and the instruction is placed into unexecutedmode (block 523). Thereafter, operation returns to block 504 in FIG. 5Ato determine whether an exit condition exists.

If the thread does not terminate in block 521, a determination is madeas to whether the instruction is JIT compiled (block 524). If theinstruction is JITed, the data gathering structure is recovered (block525) and the instruction is placed in normal mode (block 526). Noinformation is forwarded to the JIT compiler. Then, operation returns toblock 504 in FIG. 5A to determine whether an exit condition exists.

If the instruction is not JITed in block 524, a determination is made asto whether a sufficient number of samples have been gathered (block527). In this case, the instruction is placed in validation mode (block528) and operation returns to block 504 in FIG. 5A to determine whetheran exit condition exists.

If a sufficient number of samples have not yet been gathered in block527, a determination is made as to whether the class containing themethod containing the load instruction is unloaded by the virtualmachine (block 529). In this case, the data gathering structure isrecovered (block 530) and operation returns to block 504 in FIG. 5A todetermine whether an exit condition exists.

If the class is not unloaded in block 529, a determination is made as towhether the thread ID of the data gathering structure matches thecurrently executing thread (block 531). If the thread ID of thestructure does not match the current thread, no additional processingoccurs and operation returns to block 504 in FIG. 5A to determinewhether an exit condition exists. By limiting data gathering to aparticular thread, a particular processor's data cache may be exploited.

If the current thread ID matches the ID in the data gathering structurein block 531, operation proceeds to block 532 in FIG. 5D where theeffective address of the data to be loaded is calculated. The differencebetween the effective address and the last address referenced field iscalculated and the difference is divided by the size of the cache line(block 533). If the cache line size is a power of two, and it usuallyis, division can be performed simply by masking off the appropriate bitsof the address and shifting when performing the calculation. If theresult is greater than or equal to 256(2⁸−1), then it is set to thisvalue.

Then, the difference result is recorded in the differences array (block534) unless the result is zero. Thereafter, the effective address isplaced in the last address referenced field (block 535). The differencecount field is incremented (block 536). A determination is made as towhether the difference count is greater than a predetermined limit(block 537). The difference count is used to track how many samples havebeen taken. This limit is tunable. If the difference count does notexceed the limit, then no further processing occurs and operationreturns to block 504 in FIG. 5A to determine whether an exit conditionexists.

If enough samples have been collected in block 537, the virtual machinesorts the differences array (block 538). A determination is made as towhether there are a sufficient number of values in the differences array(block 539). In one preferred embodiment, the limit may be three.However, the minimum number of values for determining a striding patternmay be varied depending upon the implementation. By recording thedifferences and sorting them in the differences array, the mechanism ofthe present invention focuses on relative memory accesses, rather thantheir absolute values. For example, an example pattern of memoryaccesses may include the following:

-   -   0x100    -   0x5100    -   0xa100    -   0xf100    -   0x14100    -   . . .

The mechanism of the present invention would not get distracted by thedistance between the first and fifth access, but would determine thatone access is typically followed by another 0x5000 bytes away. If thecache line size were 1024 bytes, the differences array would hold thevalues [20, 20, 20, 20, . . . ]. Note that the first reference would bezero and, thus, not entered.

If there are fewer than three values in the differences array, thenthere are no sequences and the virtual machine recovers the datagathering structure (block 540) and places the load instruction innormal mode (block 541). Thereafter, operation returns to block 504 inFIG. 5A to determine whether an exit condition exists.

If there are at least three entries in the differences array, thevirtual machine computes the sample standard deviation (S) in thesequence (block 542). Ideally, S will be zero; however, the mechanism ofthe present invention may tolerate some non-zero value. A determinationis made as to whether S is greater than some value X (block 543). In oneexemplary embodiment, X is set to one third the mean (average) of thedifferences, although the value of X may be changed depending upon theimplementation. If the value of S is greater than X, the instruction isplaced in normal mode (block 544). No information is forwarded to theJIT. Then, the data gathering structure is recovered (block 545) andoperation returns to block 504 in FIG. 5A to determine whether an exitcondition exists.

If S is not greater than X in block 543, then the virtual machinecomputes a putative constant difference between successive accesses (B)(block 546). The value of B is computed as follows:

$B = \frac{\begin{pmatrix}{\left( {\sum{\left( {{differences}\left\lbrack {i - 1} \right\rbrack} \right)*{\sum\left( i^{2} \right)}}} \right) -} \\{\left( {N*{\left( {N + 1} \right)/2}} \right)*{\sum\left( {i*{{differences}\left\lbrack {i - 1} \right\rbrack}} \right)}}\end{pmatrix}}{\left( {\left( {N*{\sum\left( i^{2} \right)}} \right) - \left( {N*{\left( {N + 1} \right)/2}} \right)^{2}} \right)}$

Where all of the sums are for i=1 to N, which is the length of thesequence determined above. The value of B represents the putativedifference between successive accesses to the given field (the expectedcache stride) in terms of cache lines. An appropriate data validationstructure is provisioned for the instruction and the value B is copiedto it (block 547). Then, the data gathering structure is recovered(block 548) and the load instruction is placed in validation mode (block549). Thereafter, operation returns to block 504 in FIG. 5A to determinewhether an exit condition exists.

Returning to FIG. 5A, if a load instruction in validation mode isencountered in block 507, operation proceeds to block 550 in FIG. 5Ewhere a determination is made as to whether the class is unloaded. Ifthe class is unloaded, then the class is no longer being used and adetermination of cache prefetching patters will not be of use;therefore, the data validation structure for the instruction isrecovered (block 551) and the instruction is placed in normal mode(block 552). Thereafter, operation returns to block 504 in FIG. 5A todetermine whether an exit condition exists.

If the class is not unloaded in block 550, a determination is made as towhether the instruction is just-in-time (JIT) compiled (block 553). Ifthe instruction is compiled, then it is too late to provide cacheprefetch pattern information to the JIT compiler; therefore, the datavalidation structure for the instruction is recovered (block 551) andthe instruction is placed in normal mode (block 552). Thereafter,operation returns to block 504 in FIG. 5A to determine whether an exitcondition exists.

If the instruction is not JIT compiled in block 553, the effectiveaddress is computed (block 554) and the last address referenced by thecurrent thread is determined (block 555). Then, the difference betweenthe effective address and the last referenced address is computed (block556). The effective address is associated with the last referencedaddress (block 557). Next, an absolute value of the above difference interms of cache line size is computed (block 558). Note that B is roundedup to the nearest whole number.

Next, the total sample count is incremented (block 559) and adetermination is made as to whether the absolute value computed above iszero (block 560). If the absolute value is zero, then there is a directcache hit. The cache hit count is incremented (block 561) and operationcontinues to block 564. If the absolute value is not zero in block 560,then a determination is made as to whether the absolute value is B(block 562). If the absolute value is B, then the anticipated cachestride is correct, in which case the anticipated cache stride count isincremented (block 563) and operation continues to block 564. If theabsolute value is not B in block 562, then no counter is incremented andoperation continues directly to block 564.

In block 564, a determination is made as to whether a sufficient numberof samples have been gathered (block 564). This determination may bemade, for example, by comparing the total sample count to apredetermined sample limit. In the example shown in FIG. 4B, the totalsample limit is set to fifty; however, this value may he tuned to theparticular program or instruction. If a sufficient number of sampleshave not been gathered, operation returns to block 504 in FIG. 5A todetermine whether an exit condition exists.

If a sufficient number of samples have been gathered in block 564, theinstruction is placed in normal mode (block 565) and the data validationstructure is recovered (block 566). Then, the anticipated cache stridecount is divided by the total sample count minus the cache hit count(block 567). The number of cache hits is subtracted, because directcache hits do not count towards determining prefetching patterns. Thus,the anticipated cache stride count is divided by the total number ofnon-hit samples to form a percentage. This percentage is compared to athreshold (block 568). The threshold may preferably be 75%, for example.However, this value may be tuned depending upon the implementation. Forexample, 70% or any other value may be used depending upon the accuracydesired.

If the percentage is not greater than the threshold, then the cacheprefetch information is ignored and operation returns to block 504 inFIG. 5A to determine whether an exit condition exists. If the result isgreater than the threshold in block 568, then the difference array isforwarded to the JIT compiler (block 569) and operation returns to block504 in FIG. 5A to determine whether an exit condition exists.

Thus, the present invention solves the disadvantages of the prior art byproviding a mechanism that identifies instructions that access storageand may be candidates for catch prefetching. The mechanism augmentsthese instructions so that any given instance of the instructionoperates in one of four modes, namely normal, unexecuted, datagathering, and validation. In the normal mode, the instruction merelyperforms the function specified in the software runtime environment. Aninstruction in unexecuted mode, upon the next execution, is placed indata gathering mode. When an instruction in the data gathering mode isencountered, the mechanism of the present invention collects data todiscover potential fixed storage access patterns. When an instruction isin validation mode, the mechanism of the present invention validates thepresumed fixed storage access patterns.

The mechanism of the present invention presents a much cheaper andpossibly more accurate solution for obtaining stride patterns for use bya JIT compiler when generating binary code. Because the mechanism of thepresent invention records the relationship of actual memory accesspatterns regardless of data structure, it is beneficial to any type ofdata structure. The mechanism of the present invention is focused onarchitectures containing processor-specific data caches; however,multiprocessors sharing caches could also benefit from the mechanism ofthe present invention.

It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system,those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable medium of instructions and a variety of forms and thatthe present invention applies equally regardless of the particular typeof signal bearing media actually used to carry out the distribution.Examples of computer readable media include recordable-type media, suchas a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, andtransmission-type media, such as digital and analog communicationslinks, wired or wireless communications links using transmission forms,such as, for example, radio frequency and light wave transmissions. Thecomputer readable media may take the form of coded formats that aredecoded for actual use in a particular data processing system.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain theprinciples of the invention, the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A method, in a data processing system, for determining cacheprefetching patterns, the method comprising: identifying an instructionas a candidate for cache prefetching; placing the instruction in datagathering mode by changing an op-code of the instruction to form a newop-code; upon executing the new op-code, recording, in an array ofaddress differences, a difference between a current address beingreferenced and a last address being referenced, wherein the last addressbeing referenced refers to an address from the immediately previouslyexecuted op-code; and responsive to a number of address differencesbeing recorded in the array of address differences exceeding a thresholdand referring to a same cache line, determining an expected cache stridevalue based on the array of address differences.
 2. The method of claim1, wherein placing the instruction in data gathering mode includes:provisioning a data gathering structure for the instruction, wherein thearray of address differences is stored in the data gathering structure.3. The method of claim 2, further comprising: responsive to a classcontaining the instruction being unloaded, recovering the data gatheringstructure.
 4. The method of claim 2, further comprising: responsive toidentifying the instruction as the candidate for cache prefetching,placing the instruction in unexecuted mode by changing the op-code ofthe instruction to form changed op-code.
 5. The method of claim 4,wherein the step of placing the instruction in data gathering mode isperformed upon executing the changed op-code.
 6. The method of claim 4,wherein the step of provisioning the data gathering structure for theinstruction is performed upon executing the changed op-code.
 7. Themethod of claim 1, wherein the expected cache stride value is determinedusing the following equation: ${B = \frac{\begin{pmatrix}{\left( {\sum{\left( {{differences}\left\lbrack {i - 1} \right\rbrack} \right)*{\sum\left( i^{2} \right)}}} \right) -} \\{\left( {N*{\left( {N + 1} \right)/2}} \right)*{\sum\left( {i*{{differences}\left\lbrack {i - 1} \right\rbrack}} \right)}}\end{pmatrix}}{\left( {\left( {N*{\sum\left( i^{2} \right)}} \right) - \left( {N*{\left( {N + 1} \right)/2}} \right)^{2}} \right)}},$wherein B represents an expected cache stride in terms of cache linesand wherein all of the sums are for i=1 to N, wherein N is the number ofaddress differences in the array of address differences.
 8. The methodof claim 1, further comprising: responsive to the number of addressdifferences being recorded in the array of address differences exceedingthe threshold and referring to the same cache line, validating theexpected cache stride value.
 9. The method of claim 8, whereinvalidating the expected cache stride value includes: placing theinstruction in a validation mode by changing the op-code of theinstruction to form altered op-code; upon executing the altered op-code,performing the following steps: incrementing a total sample count;incrementing a cache hit count if the current address being referencedis within the same cache line as the last address being referenced;incrementing an anticipated cache stride count if the current addressbeing referenced is within the expected cache stride of the last addressbeing referenced; determining whether a sufficient number of sampleshave been considered based on the total sample count; and responsive tothe sufficient number of samples being considered, determining whether apredetermined percentage of accesses are within the expected cachestride based on the total sample count, the cache hit count, and theanticipated cache stride count.
 10. The method of claim 8, furthercomprising: responsive to the expected cache stride value being valid,providing the array of address differences to a compiler.
 11. The methodof claim 10, wherein the compiler is a just-in-time compiler.
 12. Themethod of claim 1, further comprising: responsive to the instructionbeing just-in-time compiled, placing the instruction in normal mode. 13.The method of claim 1, further comprising: responsive to the number ofaddress differences being recorded in the array of address differencesexceeding the threshold and referring to the same cache line,determining a standard deviation for the address differences in thearray of address differences; and responsive to the standard deviationexceeding a threshold, placing the instruction in normal mode.
 14. Themethod of claim 1, wherein the identifying, placing, recording, anddetermining steps are performed within a virtual machine.
 15. A computerprogram product, in a recordable-type computer readable medium, fordetermining cache prefetching patterns, the computer program productcomprising: instructions for identifying an instruction as a candidatefor cache prefetching; instructions for placing the instruction in datagathering mode by changing an op-code of the instruction to form a newop-code; instructions, upon executing new op-code, recording, in anarray of address differences, a difference between a current addressbeing referenced and a last address being referenced, wherein the lastaddress being referenced refers to an address from the immediatelypreviously executed op-code; and instructions, responsive to a number ofaddress differences being recorded in the array of address differencesexceeding a threshold and referring to a same cache line, fordetermining an expected cache stride value based on the array of addressdifferences.
 16. The computer program product of claim 15, whereinplacing the instruction in data gathering mode includes: instructionsfor provisioning a data gathering structure for the instruction, whereinthe array of address differences is stored in the data gatheringstructure.
 17. The computer program product of claim 16, furthercomprising: instructions, responsive to a class containing theinstruction being unloaded, for recovering the data gathering structure.18. The computer program product of claim 15, wherein the expected cachestride value is determined using the following equation:${B = \frac{\begin{pmatrix}{\left( {\sum{\left( {{differences}\left\lbrack {i - 1} \right\rbrack} \right)*{\sum\left( i^{2} \right)}}} \right) -} \\{\left( {N*{\left( {N + 1} \right)/2}} \right)*{\sum\left( {i*{{differences}\left\lbrack {i - 1} \right\rbrack}} \right)}}\end{pmatrix}}{\left( {\left( {N*{\sum\left( i^{2} \right)}} \right) - \left( {N*{\left( {N + 1} \right)/2}} \right)^{2}} \right)}},$wherein B represents an expected cache stride in terms of cache linesand wherein all of the sums are for i=1 to N, wherein N is the number ofaddress differences in the array of address differences.
 19. Thecomputer program product of claim 15, further comprising: instructions,responsive to the number of address differences being recorded in thearray of address differences exceeding the threshold and referring tothe same cache line, for validating the expected cache stride value. 20.The computer program product of claim 19, wherein the instructions forvalidating the expected cache stride value includes: instructions forplacing the instruction in a validation mode by changing the op-code ofthe instruction to form altered op-code; instructions, upon executingaltered op-code, for performing the following steps: incrementing atotal sample count; incrementing a cache hit count if the currentaddress being referenced is within the same cache line as the lastaddress being referenced; incrementing an anticipated cache stride countif the current address being referenced is within the expected cachestride of the last address being referenced; determining whether asufficient number of samples have been considered based on the totalsample count; and responsive to the sufficient number of samples beingconsidered, determining whether a predetermined percentage of accessesare within the expected cache stride based on the total sample count,the cache hit count, and the anticipated cache stride count.
 21. Thecomputer program product of claim 19, further comprising: instructions,responsive to the expected cache stride value being valid, for providingthe array of address differences to a compiler.
 22. The computer programproduct of claim 21, wherein the compiler is a just-in-time compiler.23. An apparatus for determining cache prefetching patterns, theapparatus comprising: means for identifying an instruction as acandidate for cache prefetching; means for placing the instruction indata gathering mode by changing an op-code of the instruction to form anew op-code; means for recording, upon executing the new op-code, in anarray of address differences, a difference between a current addressbeing referenced and a last address being referenced, wherein the lastaddress being referenced refers to an address from the immediatelypreviously executed op-code; and responsive to a number of addressdifferences being recorded in the array of address differences exceedinga threshold and referring to a same cache line, determining an expectedcache stride value based on the array of address differences.